[NTG-context] Re: international type design

It is an interesting team. 2024年4月5日 02:52, "Henning Hraban Ramm" 写到: > Have a look at these beautiful font designs: > > https://esadtype.esad-amiens.fr/ > > Unfortunately the fonts are not available (yet). > > Take your time to browse the papers about intention, design process etc. > > I

[NTG-context] international type design

Have a look at these beautiful font designs: https://esadtype.esad-amiens.fr/ Unfortunately the fonts are not available (yet). Take your time to browse the papers about intention, design process etc. I just browsed the dissertation about the (Vietnamese) "Dilinh" font and found the

[NTG-context] Re: \type ignores space between command and bracket

On 2/2/2024 11:16 AM, wolfgangbackes--- via ntg-context wrote: I have stumbeld across the same bug. Seems to be very elementary, but is still present after many years. Sigh. don't confuse bugs and features ... \starttext here a \type{\test is} done here a \type{\test [is]} done here

[NTG-context] Re: \type ignores space between command and bracket

I have stumbeld across the same bug. Seems to be very elementary, but is still present after many years. Sigh. ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist :

[NTG-context] Re: Modernizing Parametric type design A case study of Nupuram Malayalam typeface

I have created fonts for my "fictional scripts"[1] using MF[2] and "converted" them to TTF by importing the bitmap font into the background layer in Fontforge and tracing it with potrace. It was a long time ago, I used little metaness beyond setting weight through pen/path width and/or a general

[NTG-context] Re: Modernizing Parametric type design A case study of Nupuram Malayalam typeface

On 11/4/2023 9:33 AM, luigi scarso wrote: https://typoday.in/spk_papers/Santhosh_Thottingal_Typoday2023.pdf and https://twitter.com/santhoshtr/status/1577596445917470722

[NTG-context] Modernizing Parametric type design A case study of Nupuram Malayalam typeface

https://typoday.in/spk_papers/Santhosh_Thottingal_Typoday2023.pdf and https://twitter.com/santhoshtr/status/1577596445917470722 Long live to metapost & metafont (& mflua :-) :-) :-) ) -- luigi ___ If your question

[NTG-context] Arabic Type Design

interesting article: https://futuress.org/stories/arabic-typography/amp/ HR ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl /

Re: [NTG-context] Set up external figure for particular image type

On 8/1/2022 2:29 AM, Thangalin via ntg-context wrote: Got it working. Complete solution: |\setupexternalfigures[ location={local,global,default}, width=\textwidth ] \defineexternalfigure[svg][width=1cm] \defineexternalfigure[jpg][width=2cm] \defineexternalfigure[png][width=4cm] % Won't be

Re: [NTG-context] Set up external figure for particular image type

Got it working. Complete solution: \setupexternalfigures[ location={local,global,default}, width=\textwidth ]\defineexternalfigure[svg][width=1cm]\defineexternalfigure[jpg][width=2cm]\defineexternalfigure[png][width=4cm] % Won't be applied because there's no process action.% Default

Re: [NTG-context] Set up external figure for particular image type

Thangalin via ntg-context schrieb am 18.07.2022 um 19:10: Thank you, Wolfgang. That looks promising. SVG files are converted using MetaPost. I thought the following would work: svg=>{\externalfigure[#1][svg][conversion=mp]} You can probably remove the second argument ([svg]) which was

Re: [NTG-context] Set up external figure for particular image type

Thank you, Wolfgang. That looks promising. SVG files are converted using MetaPost. I thought the following would work: svg=>{\externalfigure[#1][svg][conversion=mp]} Is there anything else that needs to happen to ensure SVG files are piped through MetaPost? Thanks again! >

Re: [NTG-context] Set up external figure for particular image type

Of course, you could also use pandoc to go directly to ConTeXt; that is > currently my preferred way of producing PDF from Markdown. > Thanks Albert! I'm going to stick with my desktop text editor, KeenWrite , rather than use shell scripts

Re: [NTG-context] Set up external figure for particular image type

Thanks, Rik. Not using Pandoc. I was using Pandoc up until 2020: https://dave.autonoma.ca/blog/2019/05/22/typesetting-markdown-part-1/ I've since authored KeenWrite , which uses flexmark-java to generate XHTML

Re: [NTG-context] Set up external figure for particular image type

` function to produce the output you need. E.g., match on the file name extension use the library function `pandoc.path.split_extension` and then change the element type depending on the extension. This way you'd have all the important information in your XML. More info: <https://pandoc.org/cu

Re: [NTG-context] Set up external figure for particular image type

On 2022-07-12 14:11, Thangalin via ntg-context wrote: Thank you for the suggestion Hraban. The source comes from Markdown, which is converted to XML, then typeset using ConTeXt. There's no Markdown-specific mechanism to relate images to a particular external figure definition,

Re: [NTG-context] Set up external figure for particular image type

Thangalin via ntg-context schrieb am 12.07.2022 um 20:11: Thank you for the suggestion Hraban. The source comes from Markdown, which is converted to XML, then typeset using ConTeXt. There's no Markdown-specific mechanism to relate images to a particular external figure definition,

Re: [NTG-context] Set up external figure for particular image type

Thank you for the suggestion Hraban. The source comes from Markdown, which is converted to XML, then typeset using ConTeXt. There's no Markdown-specific mechanism to relate images to a particular external figure definition, unfortunately. All images use the same syntax and are treated the same

Re: [NTG-context] Set up external figure for particular image type

Am 08.07.22 um 17:46 schrieb Thangalin via ntg-context: I'd like to change the `maxheight` option for only PNG images, such as: Define your own figure class with \definexternalfigure: https://wiki.contextgarden.net/Command/defineexternalfigure It won’t automatically chose the file format (or

[NTG-context] Set up external figure for particular image type

external figure setups based on image type? Thank you! ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg

Re: [NTG-context] Custom type-imp file creating empty lines

Hi Pablo, Thank you so much. That was indeed the issue! Le mer. 11 mai 2022 à 19:14, Pablo Rodriguez via ntg-context < ntg-context@ntg.nl> a écrit : > On 5/11/22 18:42, Alexandre Christe via ntg-context wrote: > > Dear list, > > > > I've played a bit with a custom typ

Re: [NTG-context] Custom type-imp file creating empty lines

On 5/11/22 18:42, Alexandre Christe via ntg-context wrote: > Dear list, > > I've played a bit with a custom type-imp file (partly inspired from the > wiki https://wiki.contextgarden.net/Alegreya_Typescript > <https://wiki.contextgarden.net/Alegreya_Typescript>). However,

[NTG-context] Custom type-imp file creating empty lines

Dear list, I've played a bit with a custom type-imp file (partly inspired from the wiki https://wiki.contextgarden.net/Alegreya_Typescript). However, the file I ended up with seems to create some empty lines at the beginning of the document (if I use the default or another font this vanishes, so

Re: [NTG-context] space handling in \type

On 11/16/2021 10:53 AM, Henning Hraban Ramm via ntg-context wrote: Hi, \starttext \quotation{\type{\CONTEXT\ }} \stoptext gives “\CONTEXT \” i.e. the space moved. Why? Bug? no, side effect of catcodes ... when you use \type it will change catcodes (sort of) and when tex serializes a \cs

[NTG-context] space handling in \type

Hi, \starttext \quotation{\type{\CONTEXT\ }} \stoptext gives “\CONTEXT \” i.e. the space moved. Why? Bug? Hraban ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist

Re: [NTG-context] \type{...} as macro argument

orecurse, such that \dorecurse{10}{\type{ab c}} > > does not squash the spaces? > > Verbatim in arguments of other commands is tricky because in case with > \dorecurse the loop reads the content before it is passed to type, as a > result of this process all spaces are collapsed.

Re: [NTG-context] \type{...} as macro argument

Sylvain Hubert schrieb am 08.11.2020 um 17:56: Hi Wolfgang, I'm sorry that the question was not clear enough. Let me ask in this way: how to define a \dorecurse, such that \dorecurse{10}{\type{a    b c}} does not squash the spaces? Verbatim in arguments of other commands is tricky because

Re: [NTG-context] \type{...} as macro argument

Hi Wolfgang, I'm sorry that the question was not clear enough. Let me ask in this way: how to define a \dorecurse, such that \dorecurse{10}{\type{ab c}} does not squash the spaces? Sylvain On Sun, 8 Nov 2020 at 15:03, Wolfgang Schuster < wolfgang.schuster.li...@gmail.com> wrote: >

Re: [NTG-context] \type{...} as macro argument

Sylvain Hubert schrieb am 08.11.2020 um 14:47: Dear List, I would like to ask how to define a command, \same, such that     \same{\type{a   b c}} produces the same result as its argument does     \type{a   b c} The naive way doesn't work because it makes all the spaces collapse

[NTG-context] \type{...} as macro argument

Dear List, I would like to ask how to define a command, \same, such that \same{\type{a b c}} produces the same result as its argument does \type{a b c} The naive way doesn't work because it makes all the spaces collapse: \define[1]\same{#1} I would also like to ask whether

Re: [NTG-context] \asciimode and \type{%%}

Hans Hagen schrieb am 24.06.2020 um 21:03: But ... we can have \unexpanded\def\literalmode{\setcatcodetable\txtcatcodes} and then: [...] I'll add that command, assuming that someone will document it somewhere. Not really needed in this case but I'm going to document it. I already bet on

Re: [NTG-context] \asciimode and \type{%%}

On 6/24/2020 7:59 PM, Wolfgang Schuster wrote: Hans Hagen schrieb am 24.06.2020 um 19:06: On 6/24/2020 6:33 PM, Wolfgang Schuster wrote: Hi, when asciimode is enabled the \type command ignores double comment symbols. \starttext \quotation{\type{%}} \quotation{\type{%%}} \asciimode

Re: [NTG-context] \asciimode and \type{%%}

Hans Hagen schrieb am 24.06.2020 um 19:06: On 6/24/2020 6:33 PM, Wolfgang Schuster wrote: Hi, when asciimode is enabled the \type command ignores double comment symbols. \starttext \quotation{\type{%}} \quotation{\type{%%}} \asciimode \quotation{\type{%}} \quotation{\type

Re: [NTG-context] \asciimode and \type{%%}

On 6/24/2020 6:33 PM, Wolfgang Schuster wrote: Hi, when asciimode is enabled the \type command ignores double comment symbols. \starttext \quotation{\type{%}} \quotation{\type{%%}} \asciimode \quotation{\type{%}} \quotation{\type{%%}} \stoptext It's actually a feature: in ascimode

[NTG-context] \asciimode and \type{%%}

Hi, when asciimode is enabled the \type command ignores double comment symbols. \starttext \quotation{\type{%}} \quotation{\type{%%}} \asciimode \quotation{\type{%}} \quotation{\type{%%}} \stoptext Wolfgang

Re: [NTG-context] useexternaldocument with custom file type

Am 23.04.20 um 19:25 schrieb Henning Hraban Ramm: > >> Am 23.04.2020 um 16:36 schrieb Jan U. Hasecke : >> >> Am 23.04.20 um 16:10 schrieb Vladimir Lomov: >>> Please see the page about '\goto' command, it was written for a reason! >> >> Ok, with \goto{linkname}[program(target.doc)] it works. >> >>

Re: [NTG-context] useexternaldocument with custom file type

> Am 23.04.2020 um 16:36 schrieb Jan U. Hasecke : > > Am 23.04.20 um 16:10 schrieb Vladimir Lomov: >> Please see the page about '\goto' command, it was written for a reason! > > Ok, with \goto{linkname}[program(target.doc)] it works. > > "works" means some PDF Viewers opens the right program.

Re: [NTG-context] useexternaldocument with custom file type

Am 23.04.20 um 16:10 schrieb Vladimir Lomov: > Please see the page about '\goto' command, it was written for a reason! Ok, with \goto{linkname}[program(target.doc)] it works. "works" means some PDF Viewers opens the right program. juh

Re: [NTG-context] useexternaldocument with custom file type

icking on text in viewer? What application should be used to open a file? Take a look on page I linked in previous message. > The PDF Viewer does not support the file type. What "PDF Viewer"? For example, I use different viewers: mupdf, zathura-pdf-mupdf (zathura with mupdf pdf backend),

Re: [NTG-context] useexternaldocument with custom file type

art] \setupcolors[state=start] \starttext \goto{linkname}[file(target.doc)] \stoptext The PDF Viewer does not support the file type. TIA juh ___ If your question is of interest to others as well, please add an entry to the W

Re: [NTG-context] useexternaldocument with custom file type

Hello, ** Jan U. Hasecke [2020-04-23 12:21:27 +0200]: > Hi Wolfgang, > thanks for the fast reply. > Am 23.04.20 um 12:06 schrieb Wolfgang Schuster: >> Jan U. Hasecke schrieb am 23.04.2020 um 11:54: >>> Hi, >>> >>> can I link to a f

Re: [NTG-context] useexternaldocument with custom file type

Hi Wolfgang, thanks for the fast reply. Am 23.04.20 um 12:06 schrieb Wolfgang Schuster: > Jan U. Hasecke schrieb am 23.04.2020 um 11:54: >> Hi, >> >> can I link to a file with custom file type eg. OpenDocument with >> \useexternaldocument? >> >> This do

Re: [NTG-context] useexternaldocument with custom file type

Jan U. Hasecke schrieb am 23.04.2020 um 11:54: Hi, can I link to a file with custom file type eg. OpenDocument with \useexternaldocument? This does not work. \useexternaldocument[test][test.ods][A test document] As the PDF viewer is opened first, it does not recognize the file type

[NTG-context] useexternaldocument with custom file type

Hi, can I link to a file with custom file type eg. OpenDocument with \useexternaldocument? This does not work. \useexternaldocument[test][test.ods][A test document] As the PDF viewer is opened first, it does not recognize the file type. juh

Re: [NTG-context] \type -- extra space in TABLE

On 4/11/2020 11:44 PM, Tomas Hala wrote: Hi all, in the following code \starttext \type{6\az12}% \az = \anycommand \bTABLE \bTR\bTD\type{6\az12}\eTD\eTR \eTABLE \stoptext there is a different behaviour of \type: while its parametr in normal text is printed out as is (expected

[NTG-context] \type -- extra space in TABLE

Hi all, in the following code \starttext \type{6\az12}% \az = \anycommand \bTABLE \bTR\bTD\type{6\az12}\eTD\eTR \eTABLE \stoptext there is a different behaviour of \type: while its parametr in normal text is printed out as is (expected), in the TABLE the extra space is displayed after

Re: [NTG-context] Layer presets / size of type area

Henning Hraban Ramm schrieb am Fr., 20. Dez. 2019, 07:50: > Hi, > I setup a layer to the size of the typearea and expect the corner presets > to place my figures into the corners, but \makeupwidth/height are smaller > than the typearea (same with \textwidth). Why? > Hraban > > > \setuplayout[ >

[NTG-context] Layer presets / size of type area

Hi, I setup a layer to the size of the typearea and expect the corner presets to place my figures into the corners, but \makeupwidth/height are smaller than the typearea (same with \textwidth). Why? Hraban \setuplayout[ width=120mm, backspace=16mm, height=192mm,

[NTG-context] \type ignores space between command and bracket

Hi, in the following code example the result from \type lacks the space between \cmd and the following left bracket. \starttext \starttyping \cmd [...] \stoptyping \type{\cmd [...]} \stoptext Wolfgang

Re: [NTG-context] [dev-context] type key in \setupattachment

Zitat von Pablo Rodriguez : Sorry, Wolfgang and Hans, this was totally my fault. I even checked scrn-wid.mkiv (lines 76-93) and since I didn’t find "type", I tought it wasn’t implemented (it’s on line 112. Apparently the key is not in the interface, at least it

Re: [NTG-context] [dev-context] type key in \setupattachment

On 6/20/19 10:46 AM, Hans Hagen wrote: > On 6/19/2019 9:28 PM, Pablo Rodriguez wrote: >> [...] >> Would it be possible that the \setupattachment command has a "type" key >> to specify its MIME type? (Default should be "application/octet-stream" >> [o

Re: [NTG-context] [dev-context] type key in \setupattachment

that the \setupattachment command has a "type" key to specify its MIME type? (Default should be "application/octet-stream" [or so it seems].) This is required to add the value to the /Subtype entry in the /Embeddedfile dictionary (https://www.adobe.com/content/dam/acom/en/devnet/p

Re: [NTG-context] [dev-context] type key in \setupattachment

On 6/19/2019 9:28 PM, Pablo Rodriguez wrote: Hi Wolfgang, this comes from a previous message from this mailing list (https://mailman.ntg.nl/pipermail/dev-context/2019/003574.html), which I needed a long while to understand . Would it be possible that the \setupattachment command has a "

Re: [NTG-context] weird spacing after command type

Pablo Rodriguez schrieb am 14.10.18 um 20:38: Dear list, I have the following sample: \define[1]\slide{\startmakeup[standard]#1\stopmakeup} \definetype[texcode][style=\ttd, option=TEX] \starttext \slide{\texcode{\ifodd\pageno impar\else par\fi}}

[NTG-context] weird spacing after command type

Dear list, I have the following sample: \define[1]\slide{\startmakeup[standard]#1\stopmakeup} \definetype[texcode][style=\ttd, option=TEX] \starttext \slide{\texcode{\ifodd\pageno impar\else par\fi}} \startmakeup[standard] \texcode{\ifodd\pageno impar\else par\fi}

Re: [NTG-context] open type feature "frac"

On 9/28/2018 10:56 PM, Ulrike Fischer wrote: Due to a question on tex.sx (https://tex.stackexchange.com/questions/452969/luatex-fontfeaturefractions-on-turns-first-digits-into-superscripts) I looked again (see https://www.mail-archive.com/ntg-context@ntg.nl/msg84822.html) at the frac feature.

[NTG-context] open type feature "frac"

Due to a question on tex.sx (https://tex.stackexchange.com/questions/452969/luatex-fontfeaturefractions-on-turns-first-digits-into-superscripts) I looked again (see https://www.mail-archive.com/ntg-context@ntg.nl/msg84822.html) at the frac feature. The output is still not really satisfactory.

Re: [NTG-context] type and typing comments for TeX and Lua

On Wed, 27 Dec 2017 19:53:58 +0100, Pablo Rodriguez wrote: > could you enable issues in your Bitbucket repository? Issues are enabled now. Cheers, Christoph ___ If your question is of interest to others

Re: [NTG-context] type and typing comments for TeX and Lua

On Tue, 26 Dec 2017, Pablo Rodriguez wrote: On 12/21/2017 10:53 PM, Aditya Mahajan wrote: [...] Can you post a minimal working example. I don't use XML so it is difficult for me to understand how these commands are used in practice. Aditya, many thanks for your reply and your help. A

Re: [NTG-context] type and typing comments for TeX and Lua

On 12/21/2017 10:16 PM, Christoph Reller wrote: > > My module does not come in standard context. You have to download it > from https://bitbucket.org/philexander/context-highlight. If general > interest is high enough I can ask to > add it. Christoph, could you enable issues in your Bitbucket

Re: [NTG-context] type and typing comments for TeX and Lua

On 12/27/2017 02:14 AM, SteamedFish wrote: > You can try vim module. > > It supports all the formats that vim is able to support and it is a builtin > module. Aditya suggested this possibility to me in a previous message in this thread. But my sources are XML, so the minimal sample is more

Re: [NTG-context] type and typing comments for TeX and Lua

You can try vim module. It supports all the formats that vim is able to support and it is a builtin module. \usemodule[t-vim] \definevimtyping [TEX] [syntax=context] \definevimtyping [XML] [syntax=xml] \definevimtyping [LUA] [syntax=lua] \starttext \startTEXpage[offset=2em] a \TEX\ inline

Re: [NTG-context] type and typing comments for TeX and Lua

On 12/21/2017 10:53 PM, Aditya Mahajan wrote: > [...] > Can you post a minimal working example. I don't use XML so it is difficult > for me to understand how these commands are used in practice. Aditya, many thanks for your reply and your help. A minimal sample would be: \startbuffer[demo]

Re: [NTG-context] type and typing comments for TeX and Lua

On 12/21/2017 10:16 PM, Christoph Reller wrote: > On Thu, 21 Dec 2017 21:16:45 +0100, Pablo Rodriguez wrote: >> [...] >> It is really a pity that it lacks TeX, since I’m focused on ConTeXt yet >> (after all, it would be a Spanish introduction to ConTeXt ;-)). XML will >> come later. > > Maybe,

Re: [NTG-context] type and typing comments for TeX and Lua

On Thu, 21 Dec 2017, Pablo Rodriguez wrote: On 12/21/2017 08:05 PM, Aditya Mahajan wrote: On Thu, 21 Dec 2017, Pablo Rodriguez wrote: [...] I don’t remember which were the options in t-vim, but I need the options from \setuptyping and \setuptype. Currently vim does not support these

Re: [NTG-context] type and typing comments for TeX and Lua

On Thu, 21 Dec 2017 21:16:45 +0100, Pablo Rodriguez wrote: > On 12/21/2017 05:04 PM, Christoph Reller wrote: >> Dear Pablo, >> >> At least for XML you could use my module highlight-xml: >> >> \usemodule[highlight-xml] >> \definetype[xml][option=xml] >> [...] >> Note that even

Re: [NTG-context] type and typing comments for TeX and Lua

On 12/21/2017 08:05 PM, Aditya Mahajan wrote: > On Thu, 21 Dec 2017, Pablo Rodriguez wrote: >> [...] >> I don’t remember which were the options in t-vim, but I need the >> options from \setuptyping and \setuptype. > > Currently vim does not support these primarily because I don't use XML so > I

Re: [NTG-context] type and typing comments for TeX and Lua

On 12/21/2017 05:04 PM, Christoph Reller wrote: > Dear Pablo, > > At least for XML you could use my module highlight-xml: > > \usemodule[highlight-xml] > \definetype[xml][option=xml] > [...] > Note that even partial XML is highlighted correctly. Dear Christoph, many thanks for your reply. Your

Re: [NTG-context] type and typing comments for TeX and Lua

On 12/20/2017 10:18 PM, Hans Hagen wrote: > On 12/20/2017 8:45 PM, Pablo Rodriguez wrote: >> [...] >> Would it be possible that there are two SnippetComments for all lexers: >> SnippetCommentMark and SnippetCommentText? > > very low priority ... there is some logic behind these that i don't want >

Re: [NTG-context] type and typing comments for TeX and Lua

On Thu, 21 Dec 2017, Pablo Rodriguez wrote: On 12/20/2017 12:20 AM, Aditya Mahajan wrote: On Tue, 19 Dec 2017, Pablo Rodriguez wrote: [...] I checked your t-vim module months ago and I don’t remember which were the problems, but I had to discard it. Just try your document with t-vim. It

Re: [NTG-context] type and typing comments for TeX and Lua

On 12/20/2017 12:20 AM, Aditya Mahajan wrote: > On Tue, 19 Dec 2017, Pablo Rodriguez wrote: >> [...] >> I checked your t-vim module months ago and I don’t remember which were >> the problems, but I had to discard it. > > Just try your document with t-vim. It should be as simple as subsituting >

Re: [NTG-context] type and typing comments for TeX and Lua

--this is a comment > \stopLUA > \stopTEXpage > \stoptext > > Would it be possible that all comments in type and typing (at least, for > Lua, XML and TeX) would have the same formatting for the whole comment > contents, including the comment signs? Dear Pablo, At least f

Re: [NTG-context] type and typing comments for TeX and Lua

On 12/20/2017 8:45 PM, Pablo Rodriguez wrote: On 12/20/2017 12:53 PM, Hans Hagen wrote: On 12/18/2017 11:50 PM, Pablo Rodriguez wrote: [...] % Differs per lexer: \definestartstop [XmlSnippetComment] [color=, style=] I’m afraid that the scite module isn’t an option for

Re: [NTG-context] type and typing comments for TeX and Lua

On 12/20/2017 12:53 PM, Hans Hagen wrote: > On 12/18/2017 11:50 PM, Pablo Rodriguez wrote: >> [...] > % Differs per lexer: > > \definestartstop > [XmlSnippetComment] > [color=, > style=] > >> I’m afraid that the scite module isn’t an option for me. > > Then you need to configure

Re: [NTG-context] type and typing comments for TeX and Lua

e possible that all comments in type and typing (at least, for Lua, XML and TeX) would have the same formatting for the whole comment contents, including the comment signs? Sorry, but with the current output, it is hard to see (for total newbies) what is part of the comment and what not. And the t

Re: [NTG-context] type and typing comments for TeX and Lua

On Tue, 19 Dec 2017, Pablo Rodriguez wrote: On 12/19/2017 08:26 PM, Aditya Mahajan wrote: On Mon, 18 Dec 2017, Pablo Rodriguez wrote: [...] Would it be possible that all comments in type and typing (at least, for Lua, XML and TeX) would have the same formatting for the whole comment contents

Re: [NTG-context] type and typing comments for TeX and Lua

On 12/19/2017 08:26 PM, Aditya Mahajan wrote: > On Mon, 18 Dec 2017, Pablo Rodriguez wrote: >> [...] >> Would it be possible that all comments in type and typing (at least, for >> Lua, XML and TeX) would have the same formatting for the whole comment >> contents,

Re: [NTG-context] type and typing comments for TeX and Lua

, not \comment \stopTEX \startXML This is text. \stopXML \startLUA if code=="code" then --this is a comment \stopLUA \stopTEXpage \stoptext Would it be possible that all comments in type and typing (at least, for Lua, XML and TeX) would have the same formatting for

[NTG-context] type and typing comments for TeX and Lua

} \startTEX This is text. % a comment, not \comment \stopTEX \startXML This is text. \stopXML \startLUA if code=="code" then --this is a comment \stopLUA \stopTEXpage \stoptext Would it be possible that all comments in type and typing (at least, fo

Re: [NTG-context] changing pdf type

On Sun, Aug 6, 2017 at 7:27 PM, John Culleton wrote: > I need to have pdf files for U.S. printers in " PDF/X-1a2001" format. Hans > gave me the magic formula a few years back but I lost that reply. > Can someone help me out? > > John Culleton > > > >

[NTG-context] changing pdf type

I need to have pdf files for U.S. printers in " PDF/X-1a2001" format. Hans gave me the magic formula a few years back but I lost that reply. Can someone help me out? John Culleton ___ If your question is

[NTG-context] Possible typo in source file type-imp-lato.mkiv

defining > unknown font 'lato-reglta', loading aborted I noticed Context was searching for *reglta (with a lower case "L") rather than regita (with an "i"). Looking at the file http://source.contextgarden.net/tex/context/base/type-imp-lato.mkiv I can see that all the sy

Re: [NTG-context] Possible typo in source file type-imp-lato.mkiv

lookup 'file' fonts > defining > unknown font 'lato-reglta', loading aborted I noticed Context was searching for *reglta (with a lower case "L") rather than regita (with an "i"). Looking at the file http://source.contextgarden.net/tex/context/base/type-

Re: [NTG-context] Synchronize ERROR: unknown node type 12

Will this update also appear in the ConTeXt standalone version? Alan On Sun, Dec 20, 2015 at 10:30 AM, Akira Kakuto wrote: ... ... I have updated web2c/synctexdir/synctex-luatex.h in the TeX Live SVN to support synctex in beta-0.87.0. The latest beta-0.87.0 binaries for win32 and win64

Re: [NTG-context] Synchronize ERROR: unknown node type 12

I have updated web2c/synctexdir/synctex-luatex.h in the TeX Live SVN to support synctex in beta-0.87.0. The latest beta-0.87.0 binaries for win32 and win64 support synctex. For the other platforms, it was too late for the released beta-0.87.0 sources. SyncTeX will be supported in beta-0.87.1

Re: [NTG-context] Synchronize ERROR: unknown node type 12

On Sun, Dec 20, 2015 at 9:37 PM, Alan Bowen wrote: > Great—so how does one turn on/off synctex? > >> >>> synctex should be disabled by default; it's enabled by --synctex , i.e. $> context --synctex -- luigi

Re: [NTG-context] Synchronize ERROR: unknown node type 12

On 20 December 2015 at 22:48, luigi scarso wrote: > On Sun, Dec 20, 2015 at 9:37 PM, Alan Bowen wrote: >> >> Great—so how does one turn on/off synctex? > > synctex should be disabled by default; > it's enabled by --synctex , i.e. > > $> context --synctex Some editors (like TeXworks, TeXShop,

Re: [NTG-context] Synchronize ERROR: unknown node type 12

On 12/20/2015 10:51 PM, Mojca Miklavec wrote: On 20 December 2015 at 22:48, luigi scarso wrote: On Sun, Dec 20, 2015 at 9:37 PM, Alan Bowen wrote: Great—so how does one turn on/off synctex? synctex should be disabled by default; it's enabled by --synctex , i.e. $> context --synctex

Re: [NTG-context] Synchronize ERROR: unknown node type 12

Thanks, Luigi, Mojca. I have disabled synctex but will enable it once a version that works with the latest luatex is available for the standalone. BTW, synctex in TeXShop (which I use) does not really do much when processing prd files as I normally do. Alan On Sun, Dec 20, 2015 at 4:51 PM,

[NTG-context] Synchronize ERROR: unknown node type 12

indeed, as synctex used different node numbers than luatex (and is maintained outside the luatex source tree) ... btw as i never use synctex this went unnoticed I have updated web2c/synctexdir/synctex-luatex.h in the TeX Live SVN to support synctex in beta-0.87.0. Thanks, Akira

[NTG-context] Synchronize ERROR: unknown node type 12

Hello, I'm getting many error messages: " Synchronize ERROR: unknown node type 12 " with the latest beta: " mtx-context | warning: synctex is enabled ... This is LuaTeX, Version beta-0.87.0 (TeX Live 2016/W32TeX/dev) " and with the MWE: \starttext \section

Re: [NTG-context] Synchronize ERROR: unknown node type 12

On 12/20/2015 5:05 PM, Lukáš Procházka wrote: Hello, I'm getting many error messages: " Synchronize ERROR: unknown node type 12 " with the latest beta: " mtx-context | warning: synctex is enabled This is LuaTeX, Version beta-0.87.0 (TeX Live 2016/W32TeX/dev) &quo

Re: [NTG-context] Synchronize ERROR: unknown node type 12

Will this update also appear in the ConTeXt standalone version? Alan On Sun, Dec 20, 2015 at 10:30 AM, Akira Kakuto wrote: > indeed, as synctex used different node numbers than luatex (and is >> maintained outside the luatex source tree) ... btw as i never use synctex

Re: [NTG-context] Synchronize ERROR: unknown node type 12

Great—so how does one turn on/off synctex? Alan On Sun, Dec 20, 2015 at 11:12 AM, Hans Hagen <pra...@wxs.nl> wrote: > On 12/20/2015 5:05 PM, Lukáš Procházka wrote: > >> Hello, >> >> I'm getting many error messages: >> >> " >> Synchronize E

Re: [NTG-context] Synchronize ERROR: unknown node type 12

On 12/19/2015 6:41 PM, Lukas Prochazka wrote: Hello, I'm getting many error messages: " Synchronize ERROR: unknown node type 12 " with the latest beta: " mtx-context | warning: synctex is enabled ... This is LuaTeX, Version beta-0.87.0 (TeX Live 2016/W32TeX/dev) &quo

[NTG-context] Synchronize ERROR: unknown node type 12

Hello, I'm getting many error messages: " Synchronize ERROR: unknown node type 12 " with the latest beta: " mtx-context | warning: synctex is enabled ... This is LuaTeX, Version beta-0.87.0 (TeX Live 2016/W32TeX/dev) " and with the MWE: \starttext \section

Re: [NTG-context] section with \sethupead[section][alternative=text]; other type of section misbehaves..

section level 'three' to 'two' structuresectioning reassigning section level 'three' to 'two' I'll also add: \usemodule[structure-sections] \showstructuresections Please disregard the fact that this type of coding is bad practice! regards Keith

Re: [NTG-context] section with \sethupead[section][alternative=text]; other type of section misbehaves..

the fact that this type of coding is bad practice! regards Keith. ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman

Re: [NTG-context] section with \sethupead[section][alternative=text]; other type of section misbehaves..

type=text/css h1 {font-style: italic; font-weight: normal;} h1.part {font-style: normal; font-weight: bold;} /style body h1Heading/h1 h1 class=partPart Heading/h1/body /html [...] \setuphead[section][alternative=text] \definehead[summary][section

[NTG-context] section with \sethupead[section][alternative=text]; other type of section misbehaves..

When using \setuphead[section][alternative=text] I noticed two things: 1. There is an extra space (horizontally) directly after the section heading. I can't get a grip on how to get rid of it. 2. A different type of section (define with \definehead[summary][section] seems to alter it's behaviour

  1   2   3   4   5   >